Description

This PR introduces a significant feature enhancement to the LubeLogger application Chart by adding support for persistent data, documents, and images storage, as well as introducing additional configuration improvements.

Major Changes:

1. Persistent Volume Claims (PVC) for Data, Documents, and Images:

   • Added PVC configurations for data, documents, and images storage to enable persistence across container restarts.
   • Templates are updated to conditionally create PVCs if persistence.enabled is set to true and no existing claims are provided.
   • Deployment YAML updated to mount these PVCs within the container, allowing the application to store and retrieve data, documents, and images.

2. Version Bump:

   • Chart version bumped to 0.3.0 to reflect breaking changes and the new feature additions.

3. New Configurations:

   • Added userConfig in the values file, allowing users to specify detailed configuration options such as logging levels, authentication settings, and other.
   • Introduced translations configuration for loading translation files at runtime, enhancing internationalization capabilities.

4. Secret Handling:

   • Updated secret templates to manage configuration for user-specific settings and improved mail secret handling.
   • New secret created for storing the user configuration (userConfig), providing better separation of sensitive data.

5. Improved NOTES.txt:

   • Enhanced NOTES with warnings about potential data loss if replica count is set to more than 1, as data sync between replicas is not supported.

6. Miscellaneous:

   • Minor updates to various templates, including helper files, to accommodate the new PVCs and the initContainers for handling translations.
   • Removed unnecessary dependencies from the Brewfile.

Breaking Changes:

• The application now supports persistence, so any users who scale their deployment to multiple replicas must be aware of potential data inconsistencies, as data sync across replicas is not yet implemented.

Testing:

• PVCs were successfully created and mounted for data, documents, and images.
• Verified that translations are fetched and loaded correctly during initialization.
• Tested application behavior with persistent storage across container restarts.

Resolves #14